home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
FishMarket 1.0
/
FishMarket v1.0.iso
/
fishies
/
301-325
/
disk_313
/
uucp
/
problems.doc
< prev
next >
Wrap
Text File
|
1992-05-06
|
4KB
|
95 lines
PROBLEMS.DOC
Matthew Dillon
891 Regal Rd.
Berkeley, Ca. 94708
pacbell.PacBell.COM!sorinc!overload!dillon
MODEM AND GETTY
There are several possible sources of problems in setting up
UUCP. The major problem areas in order of likelyhood are
listed below:
(1) The modem is expecting a protocol that Getty has not
been told to use (XON/XOFF, 7WIRE, none)
If the modem uses 7-wire use the -7 option for Getty, else it is
assumed the modem uses no protocol. Normally you specify -7 but
the modem will probably work just fine whether you specify it or
not.
(2) The modem does not hangup when DTR is dropped
All modern modems hangup when DTR is dropped. Usually a dip switch
enables the option. If it is impossible to drop a connection by
dropping DTR you can use the -d0 option to make Getty use the +++
sequence. This only works if you do not specify a dumb modem in
the -M option.
(3) The modem does not understand simple AT commands or does
not generate a CONNECT message.
If the modem does understand dropping DTR but does not understand
simple AT commands or generate a CONNECT message use -c0 -Md (no
connect msg and dumb modem). In this case the baud rate must be
known and specified with one or more -B options. When no CONNECT
message is available Getty does not know what the connect baud rate
actually is. It will begin by trying the first -B option and
switch to the next whenever a line-break is received.
(4) Baud rate problems
The default modem type when no -M option is specified for Getty is
a hays modem. If you have a multimodem you can use -Mm and the
baud adjust options for Getty. Normally you specify a -B option
for each baud rate the modem is capable of connecting at. If the
modem generates a CONNECT message you need only specify one -B
option that is used to reset the modem and Getty will automatically
handle the CONNECT messages.
If your modem always talks to your Amiga at a given baud rate no
matter what the CONNECT message says then use a single -B option to
specify that baud rate then the -A option which tells getty to
ignore any baud rate specified in the CONNECT message.
OUTGOING CALLS
Unfortunately Getty handles only incomming calls. UUCico deals without
outgoing calls itself. Currently you must specify the proper baud rate
in the L.Sys file for uucico to work properly. UUCico currently ignores
any connect message.
Disconnecting will work the same way Getty handles it. If there is no
Getty running disconnecting works by dropping DTR.
NEWS
RNews currently takes a large amount of memory (the 16 bit uncompress).
At the moment there is no real solution to this problem. If you
run out of memory you may be left with queue files that did not
get uuxqt'd due to uuxqt being unable to run rnews.
MAIL ADDRESSES
If you have problems queuing mail check your L.sys file. Try emailing
to the adjacent node directly. E.G. if you can connect to 'foo' try
emailing a test message to 'foo!postmaster'. If you do not wind
up with three queue files in UUSPOOL: then your L.sys file
probably has no entry for foo. Whenever you email to somebody three
files should end up being added to UUSPOOL: and whenever you UUCico
to a given machine the spool files in question should be deleted as
they are sent. When UUCico receives mail from the remote machine it
will download the remote queue files to UUSPOOL: then uuxqt them.
That is, the remote queue files should will be placed temporarily in
UUSPOOL:, unpacked with rmail and placed in UUMAIL:, then deleted.